home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Creative Computers
/
Creative Computers CD-ROM, Volume 1 (Legendary Design Technologies, Inc.)(1994).iso
/
shareware
/
menu
/
parm_4.5
/
parm.doce
< prev
next >
Wrap
Text File
|
1994-11-17
|
28KB
|
673 lines
Documentation for ParM V4.5, SetMouse V2.1, parm.library V10.2
**************************************************************************
***************************** ********************************
***************************** WARNING ********************************
***************************** ********************************
**************************************************************************
If you use a previous release of ParM, and tools that makes use of
parm.library, you _MUST_ replace ALL theses with those given in this
release. The new parm.library version 7 is not compatable with previous
ones. It was just not possible to do it.
As promised in previous release, this new ParM only works with AmigaDOS
version 37 or higher.
ParM no more needs arp nor req libraries. OS 2.0 made it possible.
**************************************************************************
**************************************************************************
ParM stands for Parametrable Menu.
ParM allows you to build your own menus in order to run all the programs
you can have on one ore more disks. This is very useful for hard disk
owners who have programs deeply enclosed in subdirectories. With ParM,
you can run them without going through directories under either WorkBench
or CLI.
With ParM, you can start programs in either WorkBench or CLI mode. The
advantage of WorkBench mode is that the default directory of the program
you run is the one in which the program file is. But not all programs can
be run in this mode.
ParM now has an integrated SunMouse, screen blank, mouse accelerator...
We decided to implement this since an input-handler was already present in
parm.library, and we had 3 windows in the workbench screen's title bar.
One for sunmouse, one for memory/time display, and the useless ParM's
window. So now, ParM's window is usefull, and is easier to catch for menu
access.
Using ParM:
-----------
Reading this documentation can make you being confused with all modes
you can use to run your favorite tools. So, you will find at the end of
this text a tutorial about what modes you'd better use.
Installation:
-------------
Put ParM and SetMouse with their icons wherever you want, and just put
the default config file "ParM.cfg" in S: if you use it. If you
don't, you'll have to specify the config file in the command line or
in the tool types of the icon, otherwise, you will have to cancel the
requester and won't have any menus. Since version 2.6r, you must also
put parm.library in your LIBS: directory.
Running:
--------
It is recommended to run ParM from CLI if you want your programs to
have a default path other than the current directory and C: which is
the case if you start it from WorkBench.
ParM can work in three ways.
1) You can attach ParM to the CLI you are using. In this case, if you
don't specify any of the window options, the menus will be attached to
the CLI window you start it from. You may then only "Run" it to
prevent you from closing the CLI. In this case, commands launched in
RUN mode will use the cli/shell window for their input/output. If you
dont want your shell to be trashed by these commands, use the USENULL
option.
2) ParM can have its own window. This is allways the case when it is run
from WorkBench, but you can also tell it to open it's own window when
run from CLI using OWNWINDOW option or any of the window options. You
should then "RunBack" it to be able to close the CLI later.
3) ParM can be attached to Workbench, ala MyMenu.
ParM have some options which are available for most either from
WorkBench or from CLI. Arguments documentation is now available from
within ParM itself. Just type ParM ?, and then ? again. Arguments
with /S are switches, and arguments with /K are keywords and need
something more (a number, ON or OFF, a filename,...). added /N are for
numeric arguments.
From workbench, keywords are the same. You just have to add =TRUE
for switches, or =Argument for keywords.
CLIWINDOW and USENULL are not available from WorkBench.
ParM's CLI Help:
MYMENU/S,CLIWINDOW/S,OWNWINDOW/S,LEFTEDGE/K/N,TOPEDGE/K/N,DETAILPEN/K/N,BLOCKPEN/K/N,
DRAGBAR/K,DEPTH/K,AUTOFRONT/K,SHOWMEM/K,SHOWTIME/K,REFRESHTIME/K/N,MTDETAILPEN/K/N,
MTBLOCKPEN/K/N,MENUCOLOR/K/N,STACKSIZE/K/N,CONFIGFILE/K,USENULL/K: ?
ParM V4.2 © 1990-92 by S.R. & P.C.
MYMENU Attach menus to Workbench's (Like MyMenu)
CLIWINDOW Attach menus to CLI/Shell Window
OWNWINDOW Open its own window (default)
LEFTEDGE Left edge of ParM Window (default 0)
TOPEDGE Top edge of ParM Window (default 0)
DETAILPEN Detail pen of ParM Window (default 1)
BLOCKPEN Block pen of ParM Window (default 2)
DRAGBAR ON|OFF Drag bar (You can't move ParM window) (default on)
DEPTH ON|OFF Depth gadgets (default off)
AUTOFRONT ON|OFF Automatic window to front (default: on)
SHOWMEM ON|OFF Show available memory (default off)
SHOWTIME ON|OFF Show time. (default off)
REFRESHTIME Interval time for Mem/Time refresh in 0.1s (default 1s)
MTDETAILPEN DetailPen for Mem/Time (default: DetailPen)
MTBLOCKPEN BlockPen for Mem/Time (default: BlockPen)
MENUCOLOR Color for ParM's main menu (defaut: DetailPen)
STACKSIZE Default stack size for commands (defaut: ParM process stack)
CONFIGFILE Configuration file (default: S:ParM.cfg)
USENULL ON|OFF Redirect output to NULL: (or NIL:) for commands in RUN mode (default: off)
Environnement variable ParMOpt:
-------------------------------
In addition to the command line, your preferences can now be saved in
the Env:ParMOpt variable. Just snap your cli arguments and paste them
into your text editor. Then, save the file as Env:ParMOpt. This file
will be parsed first, and then the CLI/WB arguments, which will
override the environnement variable. (See example given).
Configuration file:
-------------------
You will best understand what follows if you have in front of you a
printout of the config file supplied.
A configuration file looks like a structured program. You should
indent your lines to make the file as readable as possible.
The default configuration file should be in the S: directory and be
named ParM.cfg.
The configuration file defines the menus you want, and what commands
they will run. Comments begin with a #, and continue until the end of
the line. Upper and lowercase do not make a difference.
Keywords:
---------
CMDWIN console_name
This will override the default console used for Command output
which is "CON:0000/0011/0640/0100/Command window/AUTO/CLOSE/WAIT".
This should be placed anywhere in the file but better be at top of
it. This console will in 2.0 have a close gadget, a defered open,
and wait user to hit close gadget before closing window.
Under 2.0, if you use Command in Simple mode, you MUST specify the
/WAIT option for your console, or it will close before you could
read it.
SHELLWIN console_name
This will override the default console used for SHELL commands
which is "CON:0000/0011/0640/0100/Shell/Auto/Close/Wait". This
should be placed anywhere in the file but better be at top of it.
SHORTCUTQUAL qual
This can be used to add keys to access menus short-cuts. For
example, you can use Left-Amiga, ALT, SHIFT or Ctrl. If you want
several keys, you just have to add qualifiers listed below:
Left-Shift 1
Right-Shift 2
Ctrl 8
Left-Alt 16
Right-Alt 32
Left-Amiga 64
If for example you want both left and right ALT keys to work for
menu shortcuts: ( 16 + 32 = 48 ! )